parse-imports
A blazing fast ES module imports parser.
Features
- Uses the superb WASM-based
es-module-lexer
under the
hood - Identifies module specifier types (e.g. relative file import, package import,
builtin import, etc.)
- Unescapes module specifier escape sequences
- Collects default, named, and namespace imports
- Works with dynamic imports
- Resolves module specifier paths via
require.resolve
Install
$ npm i parse-imports
Usage
import { parseImports } from 'parse-imports'
const code = `
import a from 'b'
import * as c from './d'
import { e as f, g as h, i } from '/j'
import k, { l as m } from 'n'
import o, * as p from "./q"
import r, { s as t, u } from "/v"
import fs from 'fs'
;(async () => {
await import("w")
await import("x" + "y")
})()
`
for (const $import of await parseImports(code)) {
console.log($import)
}
const imports = [...(await parseImports(code))]
console.log(imports[0])
console.log(imports[1])
console.log(imports[5])
console.log(imports[7])
console.log(imports[8])
API
Use parseImports
when you're able to await a Promise
result and
parseImportsSync
otherwise.
[!IMPORTANT]
You can only call parseImportsSync
once the WASM has loaded. You can be sure
this has happened by awaiting the exported wasmLoadPromise
.
See the type definitions for details.
Types
type ModuleSpecifierType =
| 'invalid'
| 'absolute'
| 'relative'
| 'builtin'
| 'package'
| 'unknown'
type Import = {
startIndex: number
endIndex: number
isDynamicImport: boolean
moduleSpecifier: {
type: ModuleSpecifierType
startIndex: number
endIndex: number
isConstant: boolean
code: string
value?: string
resolved?: string
}
importClause?: {
default?: string
named: string[]
namespace?: string
}
}
Import
code.substring(startIndex, endIndex)
returns the full import statement or
expression.
code.substring(moduleSpecifier.startIndex, moduleSpecifier.endIndex)
returns
the module specifier including quotes.
moduleSpecifier.isConstant
is true
when the import is not a dynamic import
(isDynamicImport
is false
), or when the import is a dynamic import where the
specifier is a simple string literal (e.g. import('fs')
, import("fs")
,
import(`fs`)
).
If moduleSpecifier.isConstant
is false
, then moduleSpecifier.type
is
'unknown'
. Otherwise, it is set according to the following rules:
'invalid'
if the module specifier is the empty string'absolute'
if the module specifier is an absolute file path'relative'
if the module specifier is a relative file path'builtin'
if the module specifier is the name of a builtin Node.js package'package'
otherwise
moduleSpecifier.code
is the module specifier as it was written in the code.
For non-constant dynamic imports it could be a complex expression.
moduleSpecifier.value
is moduleSpecifier.code
without string literal quotes
and unescaped if moduleSpecifier.isConstant
is true
. Otherwise, it is
undefined
.
moduleSpecifier.resolved
is set if the resolveFrom
option is set and
moduleSpecifier.value
is not undefined
.
importClause
is only undefined
if isDynamicImport
is true
.
importClause.default
is the default import identifier or undefined
if the
import statement does not have a default import.
importClause.named
is the array of objects representing the named imports of
the import statement. It is empty if the import statement does not have any
named imports. Each object in the array has a specifier
field set to the
imported identifier and a binding
field set to the identifier for accessing
the imported value. For example, import { a, x as y } from 'something'
would
have the following array for importClause.named
:
[{ specifier: 'a', binding: 'a' }, { specifier: 'x', binding: 'y' }]
.
importClause.namespace
is the namespace import identifier or undefined
if
the import statement does not have a namespace import.
Contributing
Stars are always welcome!
For bugs and feature requests,
please create an issue.
License
MIT ©
Tomer Aberbach
Apache 2.0 ©
Google